Access control for macrocell to femtocell handover

ABSTRACT

Access to a femtocell can be controlled as part of handover of a mobile device from macrocell to femtocell. Macro network platform issues a handover (HO) request towards femto network platform and a single virtual femto node, which represents a plurality of femto access points (APs). Location estimate(s) for the mobile device drives selection of a target femto AP. Selection of the target AP results in acceptance of the HO request. The mobile device also can request macro-to-femto (MTF) handover. HO neighbor list(s) is generated by decoding a network-issued identifier for each femto APs in a set of femtocells, and selectively ranking each femto AP based at least on channel quality; access privileges of the mobile device to each of the identified femto APs determines selectivity. Validation of mobile device&#39;s access right(s) drives acceptance of the MTF HO request to a top ranked femto AP.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims the benefit ofpriority to, each of U.S. patent application Ser. No. 13/930,000, filedJun. 28, 2013 (now U.S. Pat. No. 8,817,750), and entitled “ACCESSCONTROL FOR MACROCELL TO FEMTOCELL HANDOVER,” which is a continuation ofU.S. patent application Ser. No. 12/434,211, filed May 1, 2009 andentitled “ACCESS CONTROL FOR MACROCELL TO FEMTOCELL HANDOVER” (now U.S.Pat. No. 8,498,267, issued on Jul. 30, 2013). The entireties each of theabove-referenced applications are incorporated herein by reference.

TECHNICAL FIELD

The subject innovation relates to wireless communications and, moreparticularly, to controlling handover from macrocell to femtocell.

BACKGROUND

Indoor coverage is a primary differentiator among wireless serviceprovider, yet an indoor-environment is not conducive to efficientutilization of radio resources because of various factors such as pathloss or attenuation, which can lead to channel quality degradation andensuing excessive signaling which in turn can increase battery drainsubstantially for mobile devices operating within the indoorenvironment. In addition, as wireless service become ubiquitous and thuscommoditized, market share of legacy telecommunication systems andservice associated therewith are increasingly affected by customerattrition. Thus, various solutions such as microcells, picocells,repeaters, and femtocells have emerged to exploit legacy systems andextant broadband, non-mobile networks to provide indoor coverage.

Such solutions, particularly femtocell coverage, are likely to overlapwith extant macrocell coverage to ensure service continuity assubscriber(s) enters in and exits out of the subscriber(s) home coveragearea or private indoor environment. It is noted that while disparatesolutions such as microcells also overlapped with macro coverage, eachmicrocell required unique identifiers and handover relationships orassociations with the underlaid macrocell sector. Yet, microcells aretypically few due to cost factors limiting them to commercialapplications only. In turn, femtocells are consumer products with asignificant commoditization factor, e.g., low-threshold to marketadoption and rapid decay or adjustment of pricing setpoints; thus,femtocell deployments are projected to be far more numerous thatmicrocell solution(s). A substantive number, e.g., 10²-10⁵, offemtocells can reside within the wireless coverage area of a singlemacrocell thus creating a substantively complex handover situation fortransitioning from macrocell coverage to femtocell coverage. In view ofsuch high deployment density, handover from macrocell-to-femtocell canreadily strain conventional neighbor-handling capabilities such ashandover associations of macrocell networks and devices or othersolutions for wireless indoor coverage.

With respect to wireless network operation and handover, conventionally,public land mobile network (PLMN) and associated mobile country code(MCC) and mobile network code (MNC) or network color code(s) (NCC(s))are employed to determine if a mobile device is allowed to access amacrocell. However, conventional systems do not contemplate dedicatednetwork mask code(s) that distinguishes a “public” macrocell networkfrom a “private” femtocell network wherein a limited number of customerscan access service and related radio resources in each femto accesspoint. Conventional network operators can deploy a femto network withinthe same MNC and MCC network as a macro network. Accordingly,conventional systems can experience inefficient macro-to-femto handoverespecially in the high-density limit, e.g., 10⁵-10⁶ femtocells permacrocell that is expected in long-term deployments.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a schematic deployment of a macrocells and femtocellsfor wireless coverage, wherein macro-to-femto (MTF) handover and relatedaccess to femtocell(s) is controlled in accordance with aspectsdescribed herein.

FIG. 2 is a block diagram of an example system that enablesmacro-to-femto handover in accordance with aspects described herein.

FIG. 3 is a diagram that illustrates an example mapping of a set offemto cells deployed within a macrocell to a set of femto virtual nodesin accordance with aspects described herein.

FIG. 4 displays a block diagram of an example embodiment of a locationcomponent that enables at least in part MTF handover in accordance withaspects disclosed herein.

FIG. 5 is a block diagram of an example embodiment of a mobile devicethat can handover from macro coverage to femto coverage in accordancewith aspects described herein.

FIG. 6 is a block diagram of an example embodiment of a handovercomponent that operates in a mobile device in accordance with aspectsdescribed in the subject specification.

FIG. 7 is a block diagram of an example system that enablesmacro-to-femto handover in accordance with aspects described herein.

FIG. 8 displays a flowchart of an example method for enabling macrocellto femtocell handover according to aspects described herein.

FIG. 9 is a flowchart of an example method enabling macrocell tofemtocell handover according to aspects described herein.

FIG. 10 displays a flowchart of an example method for handing off frommacro coverage to femto coverage according to aspects described herein.

FIG. 11 is a flowchart of an example method for handing off from macrocoverage to femto coverage according to aspects described herein.

FIG. 12 is a flowchart of an example method for enabling handover frommacro coverage to femto coverage according to aspects described herein.

FIG. 13 is a flowchart of an example method for collecting location datafor a mobile device that attempts handing off from macro coverage tofemto coverage according to aspects disclosed herein.

FIG. 14 displays a flowchart of an example method for establishing, atleast in part, access to a femto access point, wherein the access can beexploited for macro-to-femto handover as described herein.

FIG. 15 is a block diagram of an example embodiment of a femtocellaccess point that can enable or exploit features or aspects described inthe subject specification.

FIG. 16 is a block diagram of an example wireless network environmentthat includes macro and femto network platforms and can implement andexploit aspects or features described herein.

DETAILED DESCRIPTION

The subject innovation is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the present innovation. It may be evident, however,that the present invention may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the presentinvention.

As used in this application, the terms “component,” “system,”“platform,” “interface,” “node,” “selector,” “generator” “layer,”“module” and the like are intended to refer to a computer-related entityor an entity related to an operational machine with one or more specificfunctionalities. The entities disclosed herein can be either hardware, acombination of hardware and software, software, or software inexecution. For example, a component may be, but is not limited to being,a process running on a processor, a processor, an object, an executable,a thread of execution, a program, and/or a computer. By way ofillustration, both an application running on a server and the server canbe a component. One or more components may reside within a processand/or thread of execution and a component may be localized on onecomputer and/or distributed between two or more computers. Thesecomponents also can execute from various computer readable media havingvarious data structures stored thereon. The components may communicatevia local and/or remote processes such as in accordance with a signalhaving one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsvia the signal). As another example, a component can be an apparatuswith specific functionality provided by mechanical parts operated byelectric or electronic circuitry that is operated by a software orfirmware application executed by a processor, wherein the processor canbe internal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components. An interface can include input/output (I/O)components as well as associated processor, application, and/or APIcomponents.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment,” “mobile station,” “mobile,”“mobile device,” “subscriber station,” “subscriber equipment,” “accessterminal,” “terminal,” “handset,” and similar terminology, refer to awireless device utilized by a subscriber or user of a wirelesscommunication service to receive or convey data, control, voice, video,sound, gaming, or substantially any data-stream or signaling-stream. Theforegoing terms are utilized interchangeably in the subjectspecification and related drawings. Likewise, the terms “access point,”“base station,” “Node B,” “evolved Node B (eNode B),” home Node B(HNB),” “home access point (HAP),” or the like, are utilizedinterchangeably in the subject specification and drawings, and refer toa wireless network component or apparatus that serves and receives data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream from a set of subscriber stations. It is noted thatin the subject specification and drawing, context or explicitdistinction provides differentiation with respect to access points orbase stations that serve and receive data from a mobile device in anoutdoor environment, and access points or base stations that operate ina confined, primarily indoor environment overlaid in an outdoor coveragearea. Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. As utilized herein, the term “prosumer”indicate the following contractions: professional-consumer andproducer-consumer.

The subject innovation provides system(s) and method(s) to controlaccess to a femtocell as part of handover of a mobile device frommacrocell to femtocell, or macro-to-femto (MTF) handover. A macronetwork platform issues a handover (HO) request towards a femto networkplatform and a single virtual femto node, which represents a pluralityof femto access points (APs). The virtual femto node is a logicalstructure that can represent various femtocells based at least in parton identifier(s) for the femto APs and capability of a mobile device todecode such identifier(s) as part of MTF HO procedure(s). It is notedthat at least one advantage of representation of femtocells throughvirtual femto node(s) is the substantive reduction of the number ofmacro-to-femto relationships or associations that are necessary as partof MTF handover.

In an aspect, location estimate(s) for the mobile device drivesselection of a target femto AP, wherein the location estimate(s) can bebased at least in part on at least one of network-requested globalnavigation satellite system (GNSS)-based measurements and triangulationconducted by the mobile device, or time-of-flight measurements ofwireless signal(s) propagation timing conducted by the macro networkplatform. Femto network platform, or one or more components thereof, canselect the target femto AP based at least in part on a proximity metricor range (e.g., nearest femto AP) to the mobile device, with theselected target femto AP located within a predetermined range from themobile device. Upon selection of the target femto AP, femto networkplatform, or one or more components thereof, can verify through anaccess list liked to the target femto AP whether the mobile device, or aunique identifier thereof, is allowed to access the selected targetfemto AP. When the mobile device, or the unique identifier thereof, inauthorized or included in the access list, the HO request is accepted orallowed and the selected target femto AP is prepared for MTF handover.Conversely, the femto network platform, or the one or more componentstherein, reject the MTF HO request.

The mobile device also can request macro-to-femto (MTF) handover. Themobile device can generate HO neighbor list(s) in accordance at leastwith decoding a network-issued unique identifier for each femto AP in aset of femtocells, and selectively ranking each femto AP based at leastin part on channel quality associated therewith. Selectivity arises fromaccess privileges of the mobile device to each of the identified femtoAPs linked at least in part to the unique identifier(s) of the femto APsand unique identifier(s) for the mobile device. Access privileges, orrights, can be linked to the unique identifier(s) of the mobile devicevia access list(s) configured at least in part through a femto networkplatform or one or more component therein. Unique identifier(s) for themobile device can be extracted as part of attachment procedures of themobile device to a serving macrocell. The mobile device generateschannel quality metrics for femto APs to which it is authorized toaccess service, thus mitigating signaling with respect to HO attempts tonon-allowed femto APs or processing related to generating channelquality for the non-allowed femto APs. Validation of mobile device'saccess right(s) drives acceptance of the MTF HO request and preparationof a top ranked target femto AP for handover.

Aspects, features, or advantages of the subject innovation can beexploited in substantially any wireless telecommunication, or radio,technology; for example, Wi-Fi, Worldwide Interoperability for MicrowaveAccess (WiMAX); Enhanced General Packet Radio Service (Enhanced GPRS);Third Generation Partnership Project (3GPP) Long Term Evolution (LTE);Third Generation Partnership Project 2 (3GPP2) Ultra Mobile Broadband(UMB); 3GPP UMTS; High Speed Packet Access (HSPA); High Speed DownlinkPacket Access (HSDPA); High Speed Uplink Packet Access (HSUPA), or LTEAdvanced. Additionally, substantially all aspects of the subjectinnovation can include legacy telecommunication technologies.

It is noted that various aspects, features, or advantages of the subjectinnovation are illustrated in connection with femto access point(s) andassociated femto network platform, such aspects or features also can beexploited in indoor-based base stations (e.g., home-based accesspoint(s), enterprise-based access point(s)) that provide wirelesscoverage through substantially any, or any, disparate telecommunicationtechnologies such as for example Wi-Fi (wireless fidelity) or picocelltelecommunication.

Referring to the drawings, FIG. 1 illustrates a wireless environmentthat includes macro cells and femtocells for wireless coverage inaccordance with aspects described herein. In wireless environment 100,two areas 105 represent “macro” cell coverage, each macro cell is servedby a base station 110. It should be appreciated that macro cells 105 areillustrated as hexagons; however, macro cells can adopt other geometriesgenerally dictated by the deployment or floor plan, geographic areas tobe covered (e.g., a metropolitan statistical area (MSA) or ruralstatistical area (RSA)), and so on. Macro coverage is generally intendedto serve mobile wireless devices, like UE 120 _(A), in outdoorslocations. An over-the-air wireless link 115 provides such coverage, thewireless link 115 comprises a downlink (DL) and an uplink (UL), andutilizes a predetermined band, licensed or unlicensed, of the radiofrequency (RF) spectrum. As an example, UE 120 _(A) can be a 3GPPUniversal Mobile Telecommunication System (UMTS) mobile phone. It isnoted that a set of base stations, its associated electronics, circuitryor components, base stations control component(s), and wireless linksoperated in accordance to respective base stations in the set of basestations form a radio access network (RAN). In addition, base station110 communicates via backhaul link(s) 151 with a macro network platform108, which in cellular wireless technologies (e.g., 3rd GenerationPartnership Project (3GPP) Universal Mobile Telecommunication System(UMTS), Global System for Mobile Communication (GSM)) represents a corenetwork.

In an aspect, macro network platform 108 controls a set of base stations110 that serve either respective cells or a number of sectors withinsuch cells. Base station 110 comprises radio equipment 114 for operationin one or more radio technologies, and a set of antennas 112 (e.g.,smart antennas, microwave antennas, satellite dish(es) . . . ) that canserve one or more sectors within a macro cell 105. It is noted that aset of radio network control node(s), which can be a part of macronetwork platform; a set of base stations (e.g., Node B 110) that serve aset of macro cells 105; electronics, circuitry or components associatedwith the base stations in the set of base stations; a set of respectiveOTA wireless links (e.g., links 115 or 116) operated in accordance to aradio technology through the base stations; and backhaul link(s) 155 and151 form a macro radio access network (RAN). Macro network platform 108also communicates with other base stations (not shown) that serve othercells (not shown). Backhaul link(s) 151 or 153 can include a wiredbackbone link (e.g., optical fiber backbone, twisted-pair line, T1/E1phone line, a digital subscriber line (DSL) either synchronous orasynchronous, an asymmetric ADSL, or a coaxial cable . . . ) or awireless (e.g., line-of-sight (LOS) or non-LOS) backbone link. Backhaulpipe(s) 155 link disparate base stations 110.

In wireless environment 100, within one or more macro cell(s) 105, a setof femtocells 125 served by respective femto access points (APs) 130 canbe deployed. While in illustrative wireless environment 100 threefemtocells are deployed per macro cell, aspects of the subjectinnovation are geared to femtocell deployments with substantive femto APdensity, e.g., 10⁴-10⁷ femto APs 130 per base station 110. A femtocell125 typically covers an area that includes confined area 145, which isdetermined, at least in part, by transmission power allocated to femtoAP 130, path loss, shadowing, and so forth. While coverage area 125 andconfined area 145 typically coincide, it should be appreciated that incertain deployment scenarios, coverage area 125 can include an outdoorportion (e.g., a parking lot, a patio deck, a recreation area such as aswimming pool and nearby space) while area 145 spans an enclosed livingspace. Coverage area typically is spanned by a coverage radius thatranges from 20 to 100 meters. Confined coverage area 145 is generallyassociated with an indoor space such as a building, either residential(e.g., a house, a condominium, an apartment complex) or business (e.g.,a library, a hospital, a retail store), which encompass a setting thatcan span about 5000 sq. ft.

A femto AP 130 typically serves a few (for example, 1-5) wirelessdevices (e.g., subscriber station 120 _(B)) within confined coveragearea 125 via a wireless link 135 which encompasses a downlink (DL) andan uplink (UL). Femto AP 130 can receive signal from a base station 110through wireless link 110. A femto network platform 109 can control suchservice, in addition to mobility handover from macro-to-femto handoverand vice versa, and registration and provisioning of femto APs. Control,or management, is facilitated by backhaul link(s) 153 that connectdeployed femto APs 130 with femto network platform 109. Backhaul pipe(s)153 are substantially the same as backhaul link(s) 151. In an aspect ofthe subject innovation, part of the control effected by femto AP 130measurements of radio link conditions and other performance metrics.Femto network platform 109 also includes components, e.g., nodes,gateways, and interfaces, that facilitates packet-switched (PS) (e.g.,internet protocol (IP)) traffic and signaling generation for networkedtelecommunication. It should be appreciated that femto network platform109 can be femto AP 130 can integrate seamlessly with substantially anypacket switched (PS)-based and circuit switched (CS)-based network suchas macro network platform 108. Thus, operation with a wireless devicesuch as 120 _(A) is substantially straightforward and seamless whenhandover from femto-to-macro, or vice versa, takes place. As an example,femto AP 130 can integrate into an existing 3GPP Core Network viaconventional interfaces, or reference links, like Iu-CS, Iu-PS, Gi, Gn.

It is to be noted that substantially all voice or data active sessionsassociated with subscribers within femtocell coverage (e.g., area 125)are terminated once the femto AP 130 is shut down; in case of datasessions, data can be recovered at least in part through a buffer (e.g.,a memory) associated with a femto gateway at the femto network platform.Coverage of a suspended or hotlined subscriber station or associatedaccount can be blocked over the air-interface. However, if a suspendedor hotlined customer who owns a femto AP 130 is in Hotline/Suspendstatus, there is no substantive impact to the customers covered throughthe subject femto AP 130. In another aspect, femto AP 130 can exploithigh-speed downlink packet access either via an interface with macronetwork platform 108 or through femto network platform 109 in order toaccomplish substantive bitrates.

In addition, in yet another aspect, femto AP 130 has a LAC (locationarea code) and RAC (routing area code) that is different from theunderlying macro network. These LAC and RAC are used to identifysubscriber station location for a variety of reasons, most notably todirect incoming voice and data traffic to appropriate pagingtransmitters, and emergency calls as well. As a subscriber station(e.g., UE 120 _(A)) that exploits macro coverage (e.g., cell 105) entersfemto coverage (e.g., area 125), the subscriber station (e.g., UE 120_(A)) attempts to attach to the femto AP 130 through transmission andreception of attachment signaling. The signaling is effected via DL/UL135; in an aspect of the subject innovation, the attachment signalingcan include a Location Area Update (LAU) and/or Routing Area Update(RAU). Attachment attempts are a part of procedures to ensure mobility,so voice calls and data sessions can be established and retained evenafter a macro-to-femto transition or vice versa. It is to be noted thatUE 120 _(A) can be employed seamlessly after either of the foregoingtransitions. In addition, femto networks typically are designed to servestationary or slow-moving traffic with reduced signaling loads comparedto macro networks. A femto service provider network 165 (e.g., an entitythat commercializes, deploys, or utilizes femto access point 130) istherefore inclined to minimize unnecessary LAU/RAU signaling activity atsubstantially any opportunity to do so, and through substantially anyavailable means. It is to be noted that substantially any mitigation ofunnecessary attachment signaling/control is advantageous for femtocelloperation. Conversely, if not successful, UE 120 _(A) is generallycommanded (through a variety of communication means) to select anotherLAC/RAC or enter “emergency calls only” mode. It is to be appreciatedthat this attempt and handling process can occupy significant UEbattery, and femto AP capacity and signaling resources (e.g.,communication of pilot sequences) as well.

When an attachment attempt is successful, UE 120 _(A) is allowed onfemtocell 125, and incoming voice and data traffic are paged and routedto the subscriber through the femto AP 130. To facilitate voice and datarouting, and control signaling as well, successful attachment can berecorded in a memory register, e.g., a Visited Location Register (VLR),or substantially any data structure stored in a network memory. It is tobe noted also that packet communication (e.g., voice and data traffic,and signaling) typically paged/routed through a backhaul broadband wirednetwork backbone 140 (e.g., optical fiber backbone, twisted-pair line,T1/E1 phone line, digital subscriber line (DSL) either synchronous orasynchronous, an asymmetric DSL, a coaxial cable . . . ). To at leastthis end, femto AP 130 is typically connected to the broadband backhaulnetwork backbone 140 via a broadband modem (not shown). In an aspect ofthe subject innovation, femto AP 130 can display status indicators forpower; active broadband/DSL connection; or any other type of backhaulconnectivity; gateway connection; and generic or specific malfunction.In another aspect, no landline is necessary for femto AP 130 operation.

FIG. 2 is a block diagram of an example system 200 that enablesmacro-to-femto (MTF) handover in accordance with aspects describedherein. In preparation for MTF handover, mobile device 240 can generatea HO neighbor list and format the list as a singleton set with an entryassociated with a single virtual femto node 275. The virtual femto node275 is a logic structure that can represent an almost arbitrary numberof femto AP(s) 270; as an example, a set of 10²-10³ femto APs can belogically consolidated into a single virtual femto node 275. In anaspect, to generate the HO neighbor list, mobile device 240 measurespilot signal(s) from a set of femto APs, e.g., femto AP(s) 270, andconsolidates the various measured femtocells into the single virtualfemto node. It should be appreciated that consolidation of measured setof femto APs into a single virtual femto node reduces therelationship(s) between the mobile device 240 and femto APs to a singleassociation irrespective of femtocell density. In addition, grouping theset of measured APs into a single virtual node reduces processing andensuing complexity at mobile device 240 since decoding identity ofmeasured femto APs can be avoided. The latter provides at least theadvantage of enabling MTF HO of conventional and legacy mobile devicesthat can scan a wireless environment. Since coverage of a femtocell andassociated femto AP is confined to an area significantly smaller thatthe area of a macro cell or sector (see FIG. 3 for an illustration),detected pilot signal(s) originates primarily from femto APs near mobiledevice 240. Accordingly, mobile device 240 can be assigned to handoff toa physical femto AP that serves a current location of the mobile device240.

Mobile device 240 can convey the HO neighbor list with the singlevirtual femto node entry through wireless link 115 to serving basestation 230, which can relay the HO neighbor list to macro networkplatform 210 via data 233 or signaling 235 transported through backhaullink(s) 151. Within macro cell network platform 210, delivery of HOneighbor list to handover manager component 212 can proceed throughcontrol node(s) 223, which can convey the HO neighbor list to servingnode(s) 218 for further relay to gateway node(s) 220 and subsequentcommunication to handover manager 212. Control node(s) 223 can befunctionally connected to access node(s) 216 through a reference link orreference interface 221. It is noted that, in an aspect, control node(s)223 can be deployed in disparate locations in the field and mutuallyconnected through backhaul pipes. In 3GPP UMTS, control node(s) areembodied in radio network controller(s). In another aspect, controlnode(s) 223 can reside at least in part within macro base stations, asit is the case in 3GPP LTE technology. It should be appreciated thatmacro network platform can include various technology layer(s) orclasses of deployments and thus control node(s) 223 include disparatetypes of nodes.

Handover manager component 212, also herein referred to as handovermanager 212, receives, as described above, the handover (HO) neighborlist with a single entry for the single virtual femto node, and cangenerate a network-initiated HO request towards femto network platform250 and the received single virtual femto node. The network-initiated HOrequest can be conveyed as part of signaling 227 and can be embodied inat least one of a short message service (SMS) communication, amultimedia messaging service (MMS) communication, an unstructuredsupplementary service data (USSD) message, or in one or more bits in atleast one of control channel(s), data packet header(s), managementframe(s), or management packet(s). It is noted that the request can becontrol-node-to-control-node request, e.g., an IuR HO request in thecase of a 3GPP UMTS architecture.

In femto network platform 250, control node(s) 253 can receive the HOrequest and relay it to handover component 254 via gateway node(s) 252,and through reference link 251. Alternatively, the control node withincontrol node(s) 223 that administers service base station 230 can conveythe HO request to access node(s) 216 which can relay it to gatewaynode(s) 252 so the HO request is conveyed to handover component 254there from. As discussed above, a physical femto AP to which mobiledevice 240 can be handed over is likely to reside in the vicinity of acurrent location of the mobile device 240. Thus, in an aspect of thesubject innovation, handover component 254 can collect locationestimate(s) of mobile device 240 in response to the received HO request.In an aspect, an indication to collect location data for the mobiledevice is signaled to macro network platform 210 via signaling 227. Theindication can be embodied in at least one of a SMS communication, a MMScommunication, a USSD communication, or one or more bits in at least oneof control channel(s), data packet header(s), management frame(s), ormanagement packet(s). Through access node(s) 216, location component 214can receive the indication to collect location data and, based at leastin part on functional capabilities of or enabled services for mobiledevice 240, it can supply location estimates based on at least one ofGNSS-based measurements or time-of-flight measurements. In the casemobile device 240 is enabled for GNSS service, e.g., mobile device 240can receive GNSS timing messages and time-stamp such messages, andimplement a triangulation algorithm, location component 214 can delivera request for a GNSS-based location estimate to the mobile device 240and receive such location estimate in response to the request. It isnoted that when mobile device 240 is unable to collect sufficient timingmessages, or GNSS fixes, to generate a location estimate due to poorsatellite visibility, location component 214 can provide timing messagesto mobile device 240. Location component 214 can deliver the receivedlocation estimate, which can be received as part of data 233 throughcontrol node(s) 223 and access node(s) 216, to handover component254—gateway node(s) 252 can receive the location estimate as part ofdata 229 and relay it to handover component 254. In an aspect, locationcomponent 214 can exploit information retained in a subscriber database(not shown) that can be part of memory 224 to determine whether mobiledevice 240 is GNSS-capable or it has GNSS service enabled. Alternativelyor additionally, in another aspect, location component 214 can querymobile device 240 for location data to which in response mobile device240 can supply a location estimate or deliver a notification thatlocation data service(s) are disabled.

In case mobile device 240 is not GNSS-capable or GNSS service is notenabled therein, location component 214 can initiate TOF measurementsand receive data associated therewith to generate, or resolve, alocation estimate for mobile device 240. Location component 214, throughaccess node(s) 216, can deliver the location estimate to handovercomponent 254—gateway node(s) 252 can receive the location estimate andrelay to handover component 254. TOF measurements assess wireless signalpropagation timing between a base station such as service base station230 and mobile device 240, and can include at least one of round triptime (RTT) measurements, time or arrival (TOA), time difference ofarrival (TDOA), angle of arrival (AOA), or the like. Location component214 can utilize timing measurements to resolve a current locationestimate for mobile device 240.

As part of access control and related MTF handover, received locationestimate(s) for mobile device 240 can be conveyed to femtocell selector258 which can compare the location estimate(s) with location records offemto APs and associated coverage areas. Femtocell selector 258 canidentify a femto AP that is located within a predetermined, configurablerange from mobile device 240, as revealed by the received locationestimate, and supply such selection of femto AP to handover component254. In response to the received selected femto AP, handover component254 can perform at least one of the following. (a) Verify through anaccess list liked to the target femto AP whether the mobile device, or aunique identifier thereof, is allowed to access the selected targetfemto AP. (b) Accept the MTF handover request when the mobile device isincluded in an access list for the selected femto AP. In an aspect, theaccess list can be included in femtocell intelligence 262. It is notedthat an access list regulates privilege(s) or right(s) of user equipmentto receive service through a femto AP. (c) Configure a user data routingpath between a control node within control node(s) 253 that cantransport data and signaling to the selected femto AP and the selectedfemto AP, such configuration can include activation of a packet dataprotocol (PDP) context for the selected femto AP. (d) Command theselected femto AP to prepare for the incoming handover, whereinpreparation can include at least one of reception and retention of datadirected towards mobile device 240, reallocation or reservation of radioresources such as bandwidth, adjustment of semi-persistent schedulingparameters, configuration of at least one transceiver and associatedcommunication circuitry to operate in radio technology in which mobiledevice 240 operates, or temporary augmentation of pilot signal(s)transmitted power so as to increase femto coverage area outside anintended confined space to increase likelihood of successful attachmentby mobile device 240.

It is noted that location records can include at least one of a geocode;a ZIP code; a street address; or a longitude, latitude and altitude. Inan aspect, femtocell selector 258 can map received location estimate(s)to location record(s) to ensure integrity of the determination oflocation of a femto AP; for instance, if a received estimate includeslatitude and longitude, femtocell selector 258 can map such estimate toa street address. Location of a femto AP can be collected, for example,at the time of provisioning the femto AP for service. Location recordscan be retained in location register 266, which can be embodied at leastin part in at least one of a subscriber database (e.g., home subscriberserver), a provisioning database that includes a femtocell identifiersuch as a service area code (SAC) (see below), or an external locationintelligence repository such as a location based service or a homesubscriber service.

Additionally, it is noted that in high-density deployment scenarios forfemtocells, TOF-based estimates can provide a broad spatial range oflocations for mobile device 240; for instance, TOF-based estimates thatinclude range from serving base station can provide a location band orlocation fringe that can range from 50 m to 500 m in width, based atleast in part on clock sources that determine, for example, chip timespan, and extend throughout a radial zone surrounding the serving basestation. It is noted that when TOF-based location estimates includeazimuth confinement, e.g., an angular interval is also estimated as partof the TOF-based location estimate, spatial resolution can remainsufficiently coarse so as to include a plurality of femto APs that laywithin the predetermined range from the mobile device 240 as provided bythe location estimate. In such scenarios, femtocell intelligence 262 canprovide a differentiator, e.g., a datum or information, that enablessuccessful identification of a satisfactory or optimal femto APcandidate for MTF HO. For instance, femtocell intelligence 262 caninclude an association between a unique identifier of mobile device 240and the residential address of a subscriber that owns or leases a femtoAP.

Upon acceptance of the HO request, handover component 254 can deliver aHO acceptance indication to macro network platform 210 trough signaling227 via link(s) 226, which can include reference link(s) or conventionalinterface(s) or link(s); access node(s) 216 can receive the indicationand relay it to handover manager 212. The indication can be embodied inat least one of a SMS communication, an MMS communication, a USSDmessage, or in one or more bits in at least one of control channel(s),data packet header(s), management frame(s), or management packet(s).Handover manager 212, in response to the acceptance indication, cancommand mobile device 240 to handover to the reported virtual femtonode; the directive to handover can include an identification, e.g.,pilot code sequence index or pilot sequence hypothesis, of the selectedphysical femto AP, wherein mobile device 240 can utilize suchidentification to encounter the selected, optimal physical femto AP. Inaddition, handover manager 212 can route data directed to mobile device240 to gateway node(s) 252 which can relay the data to a control node,part of control node(s) 253 that transport data to the optimal femto APselected for macro-to-femto (MTF) handover. When the MTF handover iscomplete, mobile device 240 is attached to the selected femto AP andreceives data through the routing data path, e.g., PDP context,configured by handover component 254.

In macro network platform 210, server(s) 222 include at least one of aprocessor, a memory, and a bus architecture, and can be functionallyconnected to each component in macro network platform 210. Server(s) 222can confer, at least in part, the described functionality of each ofsuch components and components therein. Server(s) 222 can connect to thecomponents within macro network platform 210 through bus 225 for data orany other information exchange; bus 225 can be embodied in at least oneof a memory bus, a system bus, an address bus, or one or more referencelink(s) or interface(s). Additionally or alternatively, server(s) 222can execute one or more of the components included within macro networkplatform 210. Moreover, or as another alternative, one or morecomponents that comprise macro network platform 210 can reside withinserver(s) 222. Server(s) 222 can execute, e.g., through the at least oneprocessor therein, code instructions (not shown) stored in a memory,e.g., memory 224, to provide at least in part the functionality of oneor more of the components that reside within macro network platform 210.

Memory 224 can be a memory within server(s) 222 or an external memorysuch as a memory platform in external network(s) (e.g., IP multimediasubsystem, network operations center local are network . . . )operationally coupled to the femto network platform 250.

Similarly, server(s) 256 include at least one of a processor, a memory,and a bus architecture, and can be functionally connected to eachcomponent in femto network platform 250. Server(s) 256 can confer, atleast in part, the described functionality of each of such componentsand components therein. Server(s) 256 can connect to each of thecomponents within femto network platform 250 through bus 267 for data orany other information exchange; bus 267 can be embodied in at least oneof a memory bus, a system bus, an address bus, or one or more referencelink(s) or interface(s). Additionally or alternatively, server(s) 256can execute one or more of the components included within femto networkplatform 250. Moreover, or as another alternative, one or morecomponents that comprise femto network platform 250 can reside withinserver(s) 256. Server(s) 256 can execute, e.g., through the at least oneprocessor therein, code instructions such as software or firmwareapplication(s), stored in a memory, e.g., memory 260, to provide atleast in part the functionality of one or more of the components thatreside within femto network platform 250.

Memory 260 can be a memory within server(s) 256 or an external memorysuch as a memory platform in external network(s) (e.g., IP multimediasubsystem, network operations center local are network . . . )operationally coupled to the femto network platform 250.

FIG. 3 is a diagram 300 that illustrates an example mapping of a set offemto cells deployed within a macro cell to a set of femto virtual nodesin accordance with aspects described herein. In the example mapping, aset of ten femto cells 310 ₁-310 ₁₀ served via femto APs 320 ₁-320 ₁₀and deployed in a macro cell 305 served through base station 110 aremapped to three virtual femto nodes 350. It should be appreciated thatthe number N_(AP) (an integer) of femto APs deployed in a singlemacrocell (e.g., 305) or single sector therein can range from 10²-10⁴femto APs. In a realization, mapping can be dictated at least in part bysector identifier so as to map femto APs deployed within a sector to asingle virtual femto node; for instance one of the nodes 350 can includefemto APs 320 ₉, 320 ₈, and 320 ₇. In another realization, allfemtocells within a macro cell can be mapped to a single virtual femtonode. In yet another realization a physical-to-virtual mapping canassociate all or substantially all femto APs configured to provideservice to a mobile device 330 with a single virtual femto node. In suchscenario, mappings are dynamic, with each mobile device served throughmacro coverage exposed to a unique virtual mapping. It should beappreciated that a mapping of femto APs to virtual femto nodes is atleast (i) extensible in that additional femto APs can be included in aspecific virtual node, and (ii) dynamic, with one or more physical femtoAPs added or removed based at least in part on configurable criteriasuch as sector ID, macro cell ID, provisioned address for the one ormore femto APs, or the like. As described herein, femto virtual nodescan mitigate signaling, e.g., signaling 235 or 227, associated withhandover from macro to femto coverage. A mobile device 330 cancommunicate with base station 110 via wireless link 115, and it cancommunicate through wireless link 135 the set of virtual femto nodes.

FIG. 4 displays a block diagram of an example embodiment 400 of alocation component 214 in accordance with aspects disclosed herein.Location component 214 includes a time-of-flight component 424 that canimplement measurements of wireless signal propagation timing between abase station (e.g., Node B 110) and a mobile device (e.g., device 240).Propagation timing can be assessed through various TOF metrics thatinclude at least one of round trip time (RTT), time of arrival (TOA),time difference of arrival (TDOA), or angle of arrival (AOA). TOFmetrics can be determined for FL reference signal(s) or RL soundingsignal(s). TOF component 404 can determine which type of pilot signal(s)to employ; in an aspect, such determination can be based at least inpart on at least one of channel quality or radio technology utilized forcommunication by the mobile device. Position determination functionnode(s) 428 can enable extraction of a location estimate through a TOFmetric in combination with a cell identifier (e.g., a cell globalidentifier (CGI)) or a sector identifier. It is noted that at least aportion of TOF component 404 can be distributed in the base station,e.g., as part of radio element(s) 114 to mitigate at least in part pathdelay offsets that may affect TOF estimates.

Additionally, location component 214 can include a global navigationsatellite system (GNSS) component 424 to generate, at least in part, alocation estimate for the mobile device position. GNSS component 414 canexploit PDF node(s) 424 to generate such location estimate. In anaspect, GNSS component 414 can deliver timing messages, e.g., a globalpositioning system (GPS) fix, to the mobile device (e.g., device 240) toassist it with determination of a location estimate such as latitude,longitude, or altitude.

Location component 214, and component and node(s) therein, can exploitalgorithm(s) in algorithm store 434, which when implemented, e.g.,executed by a processor, can afford to generate a location estimate orconsume location data, wherein consumption can include propagationthrough network elements, delivery to location services, or delivery toexternal networks such as law enforcement networks. It is noted that forGNSS-based location estimates, algorithm(s) can include one or morecommunication protocols that enable communication of timing messages andreceived location data 429. For TOF location estimates, based at leastin part on at least one of received timing signaling 427 or generatedtiming data, algorithm(s) can allow generation of range estimates orangular position estimates within a served area with respect to thecenterline between the base station and the mobile device.

FIG. 5 is a block diagram of an example embodiment 500 of a mobiledevice 240 that can handover from macro coverage to femto coverage inaccordance with aspects described herein. In mobile device 240, whichcan operate in multi-technology multimode, a set of antennas 509 ₁-509_(K) (K is a natural number) can receive and transmit signal(s) from andto network elements such as base stations, access terminals, wirelessports and routers, or the like, that operate in a radio access network.Antennas 509 ₁-509 _(K) are a part of communication platform 504, whichcan comprise electronic components and associated circuitry that enableprocessing and manipulation of received wireless signal(s) and wirelesssignal(s) to be transmitted. Wireless signal(s) can include traffic(e.g., a portion of data 233) and signaling such as at least a portionof signaling 235. In an aspect, communication platform 504 can receiveand deliver signaling that allows MTF handover in accordance withaspects described herein.

In an aspect, communication platform 504 includesreceiver(s)/transmitter(s) 506 that can convert signal from analog todigital upon reception, and from digital to analog upon transmission.Receiver/transmitter 506 also can divide a single data stream intomultiple, parallel data streams, or perform the reciprocal operation;such operations typically conducted in various multiplexing schemes.Functionally coupled to receiver(s)/transmitter(s) 506 is amultiplexer/demultiplexer (mux/demux) component 507 that facilitatesmanipulation of signal in time and frequency space. Electronic mux/demuxcomponent 507 can multiplex information (data/traffic andcontrol/signaling) according to various multiplexing schemes such astime division multiplexing (TDM), frequency division multiplexing (FDM),orthogonal frequency division multiplexing (OFDM), code divisionmultiplexing (CDM), space division multiplexing (SDM). In addition,mux/demux component 507 can scramble and spread information (e.g.,codes) according to substantially any code; e.g., Hadamard-Walsh codes,Baker codes, Kasami codes, polyphase codes, and so on. Amodulator/demodulator (mod/demod) component 508 also is a part ofcommunication platform 504, and can modulate information according tovarious modulation techniques, such as frequency modulation (e.g.,frequency-shift keying), amplitude modulation (e.g., M-ary quadratureamplitude modulation (QAM), with M a positive integer; amplitude-shiftkeying (ASK)), phase-shift keying (PSK), and the like. In an aspect ofembodiment 500, mod/demod component 508 is functionally coupled tomux/demux component 507. Additionally, in embodiment 500, processor(s)565 enables, at least in part, mobile device 240 to process data (e.g.,symbols, bits, or chips) for multiplexing/demultiplexing,modulation/demodulation, such as implementing direct and inverse fastFourier transforms, selection of modulation rates, selection of datapacket formats, inter-packet times, etc.

Handover component 515 can scan and decode wireless signal(s) associatedwith one or more femtocells deployed within a macrocell. A scanconducted in preparation for HO by mobile device 510 can survey andcompare signals transported in a set of electromagnetic (EM) frequencybands, which can comprise radio frequency (RF) portion(s) and microwaveportion(s) of the EM spectrum, although other spectral regions can beincluded; and a set of radio technologies. Alternatively, or inaddition, scanning of macro wireless environment can include scanningfor specific femtocell system broadcast messages linked to specifictechnologies and conveyed through disparate frequency carriers. Anetwork operator that manages at least one of a macro network platformor a femto network platform can determine the set of EM frequency bandsand radio technologies to be surveyed. Frequency bands, or frequencycarriers therein, can be added to the set of EM frequency bands as suchbands or carriers become available for communication, e.g., auctionedfor utilization or authorized for free-of-charge utilization. Similarly,as new radio technologies become standardized, or available, suchtechnologies can be introduced in the set of radio of technologies thatis surveyed.

In embodiment 500, multimode chipset(s) 545 can allow mobile device 240to operate in multiple communication modes through various radio networktechnologies (e.g., second generation (2G), third generation (3G),fourth generation (4G)) or deep-space satellite-based communication inaccordance with disparate technical specifications, or standardprotocols, for the radio network technologies or satellitecommunication. In an aspect, multimode chipset(s) 545 can utilizecommunication platform 504 in accordance with the standard protocolsspecific to a mode of operation, e.g., GNSS-based communication. Inanother aspect, multimode chipset(s) 545 can be scheduled to operateconcurrently (e.g., when K>1) in various modes or within a multitaskparadigm in which the chipset(s) operate in a dedicated mode for aspecific time interval.

Technology selector 525 can drive operation of multimode chipset(s) 545through configuration of one or more radio network technologies forcommunication in a specific telecommunication mode. In an aspect, whenmobile device 214 is enabled with GNSS service, technology selector 625exploit multimode chipset(s) 645 and communication platform 518 toreceive and process GNSS timing messages to extract a location estimatefor the mobile device 240. Processing of GNSS timing messages includesimplementation of triangulation procedure to generate the locationestimate. Switching to operation as a GNSS receiver can be initiatedthrough received signaling as part of a request received to provide alocation estimate of the mobile device 240. Such request can be part ofsignaling 235 received by serving base station 230 and relayed therefrom to the mobile device.

Mobile device 240 also includes a functional platform 555 that comprisesa set of components (not shown) that provide, at least in part, one ormore specific functionalities that complement or supplement wirelesscommunication. As an example, in a case mobile device 610 is atelephone, functional platform 555 includes functional elements such asa data entry interface (e.g., a touch screen, a keyboard, a biometricpad for biometric-based access, a microphone, a loud speaker), a camera,peripheral connectors (e.g., a universal serial bus (USB) port or anIEEE 1394 port for transferring data to a disparate device), a voicecoder-decoder (vocoder); intelligent component(s) that can respond tovoice activated command(s); and so on. It should be appreciated thatfunctional platform 555 can exploit applications (not shown) storedwithin memory 575 to provide one or more functionalities of the mobiledevice. For instance, an application can interface a subscribed withGNSS-based location estimates and associated data such as maps,landmarks, related businesses, etc.

Display interface 535, which in one or more disparate or additionalembodiments of mobile device 240 can reside within functional platform655, allows gestures for subscriber-device interaction via at least oneof a touch-responsive screen or otherwise such as a liquid crystaldisplay (LCD), a plasma panel, a monolithic thin-film basedelectrochromic display; a sound interface; or the like. Additionally,display interface 635 can render content(s) that (i) controlfunctionality of mobile device 240 as available in functional platform555, or (ii) reveal operational conditions of the mobile device 240.

Mobile device 240 also retains access intelligence 582, e.g., accesslist(s), handover log(s), or the like, in memory 575. At least a portionof such access intelligence 582 can be collected by the mobile device240, or can be received as part of a provisioning proceeding(s).

In addition, mobile device 240 includes processor(s) 565 configured toconfer, and that confer, at least in part, functionality tosubstantially any or any component, platform, interface, selector, andso forth within mobile device 240 in accordance with one or more aspectsof the subject innovation. In embodiment 500, processor(s) 565 isillustrated as external to the various functional elements of mobiledevice 240; however, processor(s) 565 can be distributed amongst suchvarious functional elements. Processor(s) 565 is functionally coupled toeach functional element (e.g., component, interface, platform, selector)and to memory 575 through bus 583, which can be embodied in at least oneof a memory bus, a system bus, an address bus, or one or more referencelink(s) or interface(s). Processor(s) 565 can store information in andretrieve information from memory 575 necessary to operate and/or conferfunctionality, at least in part, to communication platform 504, handovercomponent 515, technology selector 525, multimode chipset(s) 545,display interface 535, functional platform 555 and component therein,and other operational components (not shown) of multimode mobile device240. The information can include at least one of code instructions, datastructures, or the like.

Memory 575 can store data structures (e.g., metadata); code structure(s)(e.g., modules, objects, classes, procedures) or instructions, orsubstantially any type of software or firmware that processor(s) 565 canexecute to provide functionality associated with substantially any orany component, platform, interface, selector, and so forth, withinmobile device 240, in accordance with aspects of the subject innovation.In addition, memory 575 can retain network or device information (notshown) such as pilot signal(s) (e.g., sounding reference signal(s)); oneor more communication protocol(s) or technical specification(s); codesequences for scrambling or spreading; blind decoding hypothesis;semi-persistent scheduling parameters; frequency offsets, macro cellIDs; address book(s); or the like. Moreover, memory 575 can retaincontent(s) such as multimedia files or subscriber-generated data;security credentials (e.g., passwords, encryption keys, digitalcertificates, biometric keys such as voice recordings, iris patterns,fingerprints); hardware identifying tokens or codes such as at least oneof an international mobile subscriber identity (IMSI), a temporarymobile subscriber identity (TMSI), packet TMSI (P-TMSI), aninternational mobile equipment identifier (IMEI), a mobile directorynumber (MDN), a mobile identification number (MIN), a TelecommunicationsIndustry Association (TIA) electronic serial number (ESN), or amulti-bit identification number like the mobile identity number (MEID).It is noted that memory 575 can include stationary or removable elementssuch as a subscriber identification module (SIM) card storage, auniversal integrated circuit card (UICC) storage, or a removable useridentity module (RUIM).

Mobile device 240 also includes power supply 585, which can deliverpower to components or functional elements within mobile device 240.Power supply 585 can be a rechargeable power supply, e.g., arechargeable battery, and it can include one or more transformers toachieve power level(s) that can operate mobile device 240 andcomponents, functional elements, and related circuitry therein. In anaspect, power supply 585 can attach to a conventional power grid torecharge and ensure mobile device 240 is operational; power supply 585can include an I/O interface to operationally connect to theconventional power grid. Moreover, power supply 585 can include anenergy conversion component, such as a solar-based panel to provideadditional or alternative power resources or autonomy to mobile device240.

FIG. 6 is a block diagram of an example embodiment 600 of a handovercomponent 515 in accordance with aspects described in the subjectspecification. Wireless pilot signal(s) can originate from at least oneof femto access point(s) 270 and can be conveyed through over-the-airlink(s) 135. For femto AP(s) 270, scanner component(s) 604 can detectsignals that include DL reference signal(s) and signal strengthreport(s) generated by the femto AP(s) 270 in response to UL soundingsignal(s) conveyed by mobile device 240. Scan of signaling originated bydeployed femto APs can survey received wireless signals over a set of EMfrequency bands that can include all licensed EM frequency bands (e.g.,personal communication services (PCS), advanced wireless services (AWS),general wireless communications service (GWCS), and so forth), and allunlicensed frequency bands currently available for telecommunication(e.g., the 2.4 GHz industrial, medical and scientific (IMS) band or oneor more of the 5 GHz set of bands). Additionally, the set of radiotechnologies surveyed during the scan of indoor wireless environmentincludes one or more telecommunication technologies such as Wi-Fi,WiMAX, 3GPP2 UMB, Enhanced GPRS, 3GPP UMTS, 3GPP LTE, HSPA, HSDPA,HSUPA, or LTE Advanced.

To conduct a scan, scanner component 604 exploits at least in partcommunication platform 504. In an aspect, scanner component 604 canconfigure a transceiver component (e.g., 506) to collect signal in aspecific frequency carrier, e.g., frequency channel. Such configurationcan allow determination of downlink (DL) carrier frequency, or channelnumber. Additionally, scanner component 604 can configure demodulationand demultiplexing operation of mux/demux component 507 in accordancewith standard protocols associated with the set of disparatetelecommunication technologies that are surveyed; in an aspect, thevarious protocols and instructions necessary for implementation thereofcan reside in memory 575. Thus, demodulation and demultiplexingconfiguration enable determination of radio technology employed in DLsignal or UL signal.

It is noted that communication platform 504 can exploit, throughprocessor(s) 565, circuitry such as one or more multimode chipset(s)545, and at least a portion of processor(s) 565 to switch radiotechnologies within a configurable and upgradeable set of technologiesin order to effect telecommunication and enable a scan in accordancewith configured demodulation and demultiplexing associated with a radiotechnology. Such technology agility can afford blind determination,e.g., identification by inspection, of radio technology employed byvarious femto APs deployed within a macro cell or sector, and thusdetection of distinct virtual femto nodes pertaining to a specific radiotechnology.

Scanner component 604 can decode received wireless signals and thusdetermine a femto AP identifier code such as SAC(s) 720. In an aspect,the identifier code can be a numeric index that characterizes a pilotcode sequence, e.g., a Zadoff-Chu sequence, or an M-sequence. Decodingcan be based at least in part on blind decoding of received signal(s),computation of log-likelihood ratios (LLR) associated with constellationrealization for a specific demodulation; maximum likelihood (ML)estimation, minimum mean square equalization (MMSE), zero forcing (ZF)filtering, or maximal ratio combining (MRC) filtering. To determine codesequences and thus one or more of the foregoing identities oridentifiers, scanner component 604 can compute cross-correlation ofdecoded signal(s) and a set of code sequence hypotheses. Code sequencescan include at least one of a scrambling code, a pseudonoise (PN)sequence, a chirp-like sequence, and so forth. Code sequence hypotheses(not shown) can be retained in memory 575. When a code sequence has beendetermined, an index that identifies, for example, a decoded scramblingcode can be established as a femto AP identifier; the index can be acomposite index based at least in part on the type of decoded sequence.Scanner component(s) 212 can identify a plurality of femto APs, whichcan operate in disparate radio technologies.

To generate at least in part a list of target femto APs, or HO neighborlist(s) 578, scanner component 604 also can convey, throughcommunication platform 504, UL sounding signal(s) to a group of one ormore identified femto APs and receive UL signal quality report(s)associated with the conveyed UL sounding signal(s). Such reports can (i)be embodied in a SMS communication, a MMS communication, a USSD message,or in one or more bits in at least one of control channel(s), datapacket header(s), management frame(s), or management packet(s), and (ii)received through signaling via wireless link(s) 135.

Channel quality indicator (CQI) component 614 can evaluate at least oneof quality or strength of scanned wireless pilot signal(s) originatingfrom a set of neighboring femto APs (e.g., 270). Signal strength can bedetermined through received signal strength indicators (RSSIs) orreceived signal code power (RSCP), while quality can be assessed throughmetrics such as signal-to-noise ratio (SNR),signal-to-noise-and-interference ratio (SNIR), or energy per chip overtotal received power (E_(c)/N₀). In an aspect, CQI component 614 cananalyze noise measurements effected by scanner component 604 to extractnoise features such as spectral profile, noise amplitude, statistics,etc., and therefore generate at least in part the foregoing channelquality metrics.

To produce, at least in part, a list of target femto APs formacro-to-femto handover, target generator component 624, also hereinreferred to as target generator 624, can rank a set of one or more ofthe surveyed femto APs in accordance at least in part with one or moreof the channel quality metrics generated by CQI component 614. Targetgenerator component 624 can exploit such ranking to produce HO neighborlist(s) 578 and retain such list(s) in memory 575. In addition, targetgenerator component 624 can cast at least a portion of HO neighborlist(s) 578 as virtual femto node(s), which, as discussed above, mobiledevice 240 can report to macro network platform 210 as part of handoverproceedings.

Handover (HO) driver component 634, referred herein also as HO driver634, can manage handover signaling that allows at least one of scanningof wireless environment and femto APs deployed therein, attachment to aspecific femto AP and detachment from a serving base station, e.g., 230,or selection of one or more femto APs within HO neighbor list(s) 578 orvirtual femto node(s) therein.

In embodiment 600 of handover component 515, two or more componentstherein can be functionally coupled through a bus 635 to exchange atleast one of data and signaling; bus 635 can be embodied in at least oneof a memory bus, a system bus, an address bus, or one or more referencelink(s) or interface(s).

FIG. 7 is a block diagram of an example system that enablesmacro-to-femto handover in accordance with aspects described herein. Inaddition to location-based MTF HO driver, identifying information forfemto APs can be employed as described herein to control access to afemtocell upon MTF handover. Utilization of such identificationinformation relies at least in part on capability(ies) of a mobiledevice, e.g., 240, to extract a unique identifier for femtocell. In anaspect, identification (ID) generator component 710, also hereinreferred to as identification generator 710, can assign each provisionedfemtocell a unique service area code (SAC) 720, and configure accessprivileges, e.g., “authorized full access,” “authorized restrictedaccess,” “access denied,” or the like, for a mobile device to accesseach femtocell based at least in part on the unique SAC associatedtherewith. Access privileges for a mobile device can be recorded inaccess list(s) 714, which links access privileges for a mobile device240 with a unique identifier thereof—generally, customer(s) authorizedin a particular femtocell or associated access point(s) can be grantedradio resources. Such unique identifier can include at least one of anIMSI, a TMSI, a P-TMSI, an IMEI, an MDN, a MIN, TIA ESN, or a multi-bitMEID. It is noted that, in an aspect, access privileges allow emergencycalls to be served by each provisioned femto AP regardless identifier(s)of a mobile device that places the call. It is also noted that femtonetwork platform 250 can deliver, via gateway node(s) 252 and throughlink(s) 226, one or more access list(s) 714 to macro network platform210, which can relay the one or more access list(s) 714 to a mobiledevice, e.g., device 240; the one or more access list(s) 714 can beretained as part of access intelligence 582 within mobile device 240.

Configured unique SAC can allow, at least in part, MTF handover ofmobile device 240. As described supra, mobile device 240 can scanneighbor femto APs as part of MTF handover preparation in order togenerate a HO neighbor list; scanning can be effected by scannercomponent 604, which can be part of handover component 515. In anaspect, as part of generation of the HO target list, mobile device 240scans and decodes pilot signal(s) from a set of neighbor femto APs toextract, or decode, SAC(s) 720 for each femto AP in the set, e.g., femtoAP(s) 270. Based at least in part on SAC information and related accessprivileges, mobile device 240 can selectively scan pilot signal(s) todetermine channel quality or signal(s) condition for femto APs in theset of neighbor femto APs to which the mobile device 240 is authorizedto access. It should be appreciated that assessment of channel qualitytypically exerts higher battery drain that decoding a SAC or most anyunique identifier for the femto AP. Accordingly, SAC information andrelated selective scanning allow mobile device 240 to skip, or avoid,measuring at least one of pilot signal(s) or system message(s) forneighbor femto APs, or femtocells, that mobile device 240 is not allowedto access as established through access list(s) 714. Thus ensuing anenhanced battery lifetime with respect to scanning-intensive generationof a HO neighbor list. Scanning of authorized femto APs by mobile device240 enable generation of the HO neighbor list, as described above inconnection with handover component 515.

Additionally, macro network platform 210, via handover manager 212, canexploit shared network area (SNA) access information to extract theidentity of mobile device 240. In an aspect, the identity of mobiledevice 240 can be retrieved by the macro network platform 210 based onat least one of IMSI, TMSI, P-TMSI information sent in signalingmessages, e.g., as part of attachment to a serving macro base station,e.g., 230. It is noted that macro network platform 210 can exploit otherunique identifiers for the mobile device such as IMSI, MDN, MIN, ESN,MEID, or the like.

To implement MTF handover of mobile device 240, handover manager 212 cancheck the extracted identity of mobile device 240 with a selected targetfemto AP identifying information based at least in part on at least oneof assigned SAC(s) 720, femtocell ID, femtocell intelligence 262, orconfigured features of access list(s) 714. It should be appreciated thatat such validation stage of MTF handover, mobile device 240 is likely tobe authorized to access the selected target femto AP otherwise it willnot measure pilot signal(s) from and assess channel quality of theselected target femtocell. Upon authorization, mobile device 240 conveysa MTF handover request to the selected femto AP to macro networkplatform 210. MTF handover request can be received by control node(s)223 as part of signaling 235. Control node(s) 223 relay, throughreference link 221, the MTF handover request to access node(s) 216 whichcommunicate the MTF HO request to handover manager 212. Since the mobile240 is authorized to access the selected target femto AP, handovermanager 212 conveys the request to gateway node(s) 252, throughsignaling 227, and the request is relayed to handover component 254.Handover component 254 can confirm access privileges of mobile device240 to the selected femto AP and accept, or grant, the MTF HO request.As a result, handover component 254 can prepare at least one of a femtogateway node, a femto control node, or the selected femto AP for MTF HOof the mobile device. Preparation can include aspects described supra.

When mobile device 240 is not authorized to access the selected targetfemto AP, a mobile-initiated relocation request is rejected prior tomobile device 240 camping, or effecting a successful attachmentprocedure, on the selected target femto AP and requesting radioresources. Thus, such validation stage can serve as a redundancy layer,or additional check, to ensure adequate MTF HO authorization of therelocation request. Upon rejection of a delivered MTF handover request,mobile device 240 can update a target femto AP based at least in part onthe generated HO neighbor list and attempt MTF handover. Mobile device240 can effect a finite number of MTF handover attempts, the numberupper bounded by the number of candidate target femto APs in thegenerated HO neighbor list.

At least one advantage of selective scanning of pilot signal(s) asdictated at least in part by SAC(s) 720 is mitigation of signalingbetween a mobile device and candidate, or target, femto APs with ensuingincrease in battery life of the mobile device, and reduction ofprocessor(s) load therein. Additionally, it is noted that signaling isreduced at least in part as a result of attempts from the mobile deviceat MTF handover towards authorized target femtocell(s) without attemptedHOs to unauthorized femtocells, which can lead to rejection of suchattempted HOs.

Handover component 254 can exploit artificial intelligence (AI) ormachine learning methods in addition to historical data on MTF handoverto infer (e.g., reason and draw a conclusion based upon a set ofmetrics, arguments, or known outcomes in controlled scenarios) asatisfactory or optimal femto AP to serve a mobile device that undergoesmacro-to-femto HO; a suitable range between a candidate target femto APand a mobile device that implements MTF HO; or a pilot signal(s)transmission power and time interval to increase likelihood of a mobiledevice attachment to a selected femto AP. Historical MTF HO data can beretained as part of a MTF HO log generated at least in part uponsuccessful macro-to-femto handover by a mobile device, e.g., mobiledevice 240, and stored in memory 260 or memory 224.

Artificial intelligence techniques typically apply advanced mathematicalalgorithms—e.g., decision trees, neural networks, regression analysis,principal component analysis (PCA) for feature and pattern extraction,cluster analysis, genetic algorithm, or reinforced learning—to a dataset. In particular, handover component 254 or any component(s) thereincan employ one of numerous methodologies for learning from data and thendrawing inferences from the models so constructed. Such methodologiescan be retained in memory 260. For example, Hidden Markov Models (HMMs)and related prototypical dependency models can be employed. Generalprobabilistic graphical models, such as Dempster-Shafer networks andBayesian networks like those created by structure search using aBayesian model score or approximation can also be utilized. In addition,linear classifiers, such as support vector machines (SVMs), non-linearclassifiers like methods referred to as “neural network” methodologies,fuzzy logic methodologies can also be employed. Moreover, game theoreticmodels (e.g., game trees, game matrices, pure and mixed strategies,utility algorithms, Nash equilibria, evolutionary game theory, etc.) andother approaches that perform data fusion, etc., can be exploited.

In view of the example systems described above, example methods that canbe implemented in accordance with the disclosed subject matter can bebetter appreciated with reference to flowcharts in FIGS. 8-14. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methodologies.Furthermore, not all illustrated acts may be required to implement adescribed example method in accordance with the subject specification.Further yet, two or more of the disclosed example methods can beimplemented in combination with each other, to accomplish one or morefeatures or advantages herein described. It should be furtherappreciated that the example methods disclosed throughout the subjectspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methodologies tocomputers for execution, and thus implementation, by a processor or forstorage in a memory.

FIG. 8 displays a flowchart of an example method 800 for enabling accesscontrol to a femto access point as part of macrocell to femtocellhandover according to aspects described herein. One or more networkcomponents (e.g., handover manager 212, server(s) 222, handovercomponent 236, server(s) 240) can implement the subject example method800. Additionally or alternatively, at least one processor that confers,at least in part, functionality to the one or more network componentscan enact the subject example method 800. At act 810, a macro-to-femto(MTF) handover (HO) list with a single virtual femto node is received.Reception of the MTF HO list can be part of a MTF HO request, and can bereceived from a mobile device served by a macrocell base station. At act820, a MTF HO request towards the received virtual femto node isdelivered. At act 830, a location estimate is supplied for a wirelessdevice associated with the MTF HO request. In an aspect, locationestimate can be supplied through a location component (e.g., component214) which can be part of the one or more network components that canenact the subject example method 800. Location estimates can be based atleast in part on at least one of GNSS location estimates or TOF locationestimates; related position determination functions and associated nodesthat implement one or more of the PDFs can generate the locationestimates. TOF estimates can include RTT, TOA, TDOA, AOA determinedthrough DL or UL pilot signal(s).

At act 840, it is determined if acceptance of MTF HO request isreceived. In an aspect, Acceptance can be indicated through signaling227 via an ACK (acknowledge); ACK signaling can be embodied, forexample, in one or more reserved bits in a packet header, alight-payload (e.g., of the order of 1 byte) data packet, apredetermined multi-bit word conveyed in a radio frame within a controlchannel, etc. In the negative case, exception handling is implemented atact 850. Implementation of exception handling can include implementationof a retry cycle in which a predetermined number M, an integer, of MTFHO requests are attempted at predetermined intervals until the requestis accepted or M attempts are completed. In the affirmative case, at act860, the mobile device associated with the MTF HO request is commandedto handover from macro coverage to the virtual femto node. At act 870,traffic and signaling intended to the requester wireless device isrouted to a macro-to-femto handover connection.

FIG. 9 is a flowchart of an example method 900 enabling macrocell tofemtocell handover according to aspects described herein. One or morenetwork components (e.g., handover manager 212, server(s) 222, handovercomponent 236, server(s) 240) can implement the subject example method900. Additionally or alternatively, at least one processor that confers,at least in part, functionality to the one or more network componentscan enact the subject example method 900. At act 910, a MTF HO requesttowards a target femto access point (AP) is received from a mobiledevice. At act 920, an identity for the mobile device that conveys theMTF HO request is extracted. The identity can include at least one of atleast one of an IMSI, a TMSI, a P-TMSI, an IMEI, an MDN, a MIN, an ESN,or a multi-bit identification number such as a MEID. At act 930, it isevaluated if the mobile device is authorized to access the target femtoAP. In the negative case, the MTF HO request is rejected act 940. In theaffirmative case, at act 950, macro-to-femto HO to the target femto APis authorized. An authorization indication can be conveyed throughsignaling 235 via an ACK (acknowledge); ACK signaling can be embodied,for example, in one or more reserved bits in a packet header, alight-payload (e.g., of the order of 1 byte) data packet, apredetermined multi-bit word conveyed in a radio frame within a controlchannel, etc. At act 960, traffic and signaling intended to the mobiledevice is routed to a macro-to-femto HO connection.

FIG. 10 displays a flowchart of an example method 1000 for handing offfrom macro coverage to femto coverage according to aspects describedherein. A mobile device or one or more components therein can enact thesubject example method 1000. Additionally or alternatively, at least oneprocessor that confers, at least in part, functionality to the mobiledevice or the one or more components therein can enact the subjectexample method 1000. At act 1005, pilot signal(s) from a set of femtoaccess points is measured. In an aspect, pilot signal(s) are measured onat least one of a set of radio technologies and a set of frequencybands, either licensed or unlicensed. Measurements to be conducted canbe specified, at least in part, in a scan configuration retained withina memory, removable or otherwise, of the mobile device that enacts thesubject example method 1000. At act 1010, a single virtual femto node ina handover neighbor list is reported. At act 1015, an indication isreceived to supply location data. Such an indication can be conveyed aspart of signaling 235 to a macro base station that serves the mobiledevice that enacts the subject example method; the macro base stationcan relay the indication to the mobile device through an over-the-airlink (e.g., wireless link 115).

At act 1020, it is determined if location data service is enabled. Thedetermination can be effected by the mobile device that enacts thesubject example method 1000 in response to the indication to supplylocation data at act 1015. In the negative case, location data servicedisabled is notified at act 1025. At act 1035 an indication to delivertime-of-flight (TOF)-related signaling is received. The indication canbe part of measurement(s) of propagation timing of wireless signal(s)included in TOF measurements. At act 1045, TOF-related signaling isdelivered and flow is directed to act 1055. Conversely, when outcome ofact 1020 is positive, a location estimate is conveyed at act 1040. In anaspect, conveying the location estimate can include receiving GNSS-basedtiming messages and time-stamping reception of the GNSS-based timingmessages to implement, at least in part, triangulation of the mobiledevice that enacts the subject example method to generate the locationestimate. At act 1055, a command to handover to a specific femto APwithin the virtual femto node is received.

At act 1060, attachment to the specified femto AP occurs. To effectattachment to the femto AP, the mobile device the enacts that subjectexample method 1000 exchanges control signaling that enables, forexample, LAU and RAU in order to access radio resources provided throughthe specified femto AP. At act 1065, detachment from a serving macrocell is effected. In an aspect, as part of detachment, the mobile devicethat enacts the subject example method 1000 can request at least one ofrevocation of granted, or scheduled, radio resources; termination ortransfer of active radio bearers; or data transfer to a macro-to-femtoconnection and associated serving node(s) and gateway node(s) within afemto network platform that administers, at least in part, the specifiedfemto AP.

FIG. 11 is a flowchart of an example method 1100 for handing off frommacro coverage to femto coverage according to aspects described herein.A mobile device or one or more components therein can enact the subjectexample method 1100. Additionally or alternatively, at least oneprocessor that confers, at least in part, functionality to the mobiledevice or the one or more components therein can enact the subjectexample method 1100. At act 1110, pilot signals from a first set offemto APs are scanned. In an aspect, pilot signal(s) are measured on atleast one of a set of radio technologies and a set of frequency bands,either licensed or unlicensed. Measurements can be specified, at leastin part, in a scan configuration retained within a memory (e.g., memory575), removable or otherwise, of the mobile device that enacts thesubject example method 1100. At act 1120, a service area code (SAC) isidentified for each femto AP in the set of femto APs. At act 1130, atarget femtocell list is generated in accordance at least in part withmeasured pilot signals from a second set of femto APs selected inaccordance at least in part with an identified set of SACs. At act 1140,a request to handover to a specific femto AP within the target femtocelllist is conveyed.

At act 1150, it is probed if the request is granted. One or more networkcomponents, e.g., handover manager 212, can grant or deny the request.In an aspect, the request can be indicated through signaling 235 via anACK signal; ACK signaling can be embodied, for example, in one or morereserved bits in a packet header, a light-payload (e.g., of the order of1 byte) data packet, a predetermined multi-bit word conveyed in a radioframe within a control channel, etc. When the request is denied, the HOrequest to a specific femto AP within the target femtocell list isupdated at act 1160. The update can be directed to requesting handoff toa disparate femto AP in the target femtocell list. At act 1164, it isdetermined if a number of updates is above threshold, the threshold canbe configurable by a network operator or can be established by thecardinality of the set of target femto APs in HO neighbor list. In theaffirmative case, exception handling is implemented at act 1168.Implementation of exception handling can include implementation of aretry cycle in which a predetermined number M, an integer, of MTF HOrequests are attempted at predetermined intervals until the request isaccepted or M attempts are completed. Conversely, in the negative case,flow is directed to act 1140 upon updating the request.

When the request is granted at act 1150, attachment to the specifiedfemto AP occurs at act 1170. To effect attachment to the femto AP, themobile device the enacts that subject example method 1000 exchangescontrol signaling that enables, for example, LAU and RAU in order toaccess radio resources provided through the specified femto AP. At act1180, detachment from a serving macrocell is effected. In an aspect, aspart of detachment, the mobile device that enacts the subject examplemethod 1000 can request at least one of revocation of granted, orscheduled, radio resources; termination or transfer of active radiobearers; or data transfer to a macro-to-femto connection and associatedserving node(s) and gateway node(s) within a femto network platform thatadministers, at least in part, the specified femto AP.

FIG. 12 is a flowchart of an example method 1200 for enabling handoverfrom macro coverage to femto coverage according to aspects describedherein. One or more network components (e.g., handover component 236,server(s) 240, handover manager 212, server(s) 222) can implement thesubject example method 1200. Additionally or alternatively, at least oneprocessor that confers, at least in part, functionality to the one ormore network components can enact the subject example method 1200. Atact 1210, a MTF HO request linked to a mobile device served through amacro mobile network is received. At act 1220, location data iscollected for the mobile device. At act 1230, based at least in part onthe collected location data, a femto AP that is adequate to serve themobile device is selected. In an aspect, adequacy is gauged based atleast in part on a geographical distance from the mobile device. At act1240, it is evaluated if the mobile device is located within apredetermined range from the selected femto AP. The predetermined rangecan be configurable by a network operator. In an aspect, thepredetermined range can depend at least in part on transmit power forpilot signal(s) of the selected femto AP; the one or more networkcomponents that enact the subject method 1200 can autonomously establisha transmit power that minimizes attachment time to the selected femto APwhile interference, as measured through noise amplitude, withneighboring femto APs remains below a threshold. When the evaluationoutcome is negative, exception handling is implemented at act 1250.Implementation of exception handling can include at least one ofrejection of the HO request; implementation of a retry cycle in which apredetermined number M, an integer, of MTF HO requests are attempted atpredetermined intervals until the request is accepted or M attempts arecompleted; or notification procedure(s) to the mobile device or anetwork component within macro network platform or femto networkplatform. Conversely, at act 1260, it is determined if the mobiledevice, or a unique identifier thereof, is included in an access listlinked to the selected femto AP. In the affirmative case, when themobile device is included in the access list linked to the selectedfemto AP, the received MTF HO request is accepted at act 1270. In anaspect, acceptance can be indicated through signaling 235 via an ACKsignal; ACK signaling can be embodied, for example, in one or morereserved bits in a packet header, a light-payload (e.g., of the order of1 byte) data packet, a predetermined multi-bit word conveyed in a radioframe within a control channel, etc.

At act 1280, preparation for handover of the mobile device to theselected femto AP is effected. In an aspect, preparation can include atleast one of reception and retention of data directed towards the mobiledevice; reallocation or reservation of radio resources such asbandwidth; adjustment of semi-persistent scheduling parameters;configuration of at least one transceiver and associated communicationcircuitry to operate in a radio technology in which the mobile deviceoperates; or temporary augmentation of pilot signal(s) transmitted powerso as to increase femto coverage area outside an intended confined spaceto increase likelihood of successful attachment by the mobile device.

FIG. 13 is a flowchart of an example method 1300 for collecting locationdata for a mobile device that attempts handing off from macro coverageto femto coverage according to aspects disclosed herein. One or morenetwork components (e.g., location component 214, server(s) 222,femtocell selector 238, server(s) 222) can implement the subject examplemethod 1300. Additionally or alternatively, at least one processor thatconfers, at least in part, functionality to the one or more networkcomponents can enact the subject example method 1300. At act 1310, it isdetermined if the mobile device is enabled with GPS service. In theaffirmative case, GPS location data is requested for the mobile deviceat act 1320. In an aspect, a request is generated from one or morecomponents within a femto network platform 250 and conveyed throughsignaling 229 to a location component (e.g., component 214) or alocation server, which can be part of server(s) 222. At act 1330, a GPSlocation estimate for the mobile device is received. The mobile devicecan generate the GPS location estimate. Conversely, when outcome toevaluation act 1310 is negative, location data for the mobile devicebased at least in part on one or more time-of-flight (TOF) measurementsis requested at act 1340. At act 1350, a location estimate for themobile device based at least in part on the one or more TOF measurementsis received.

FIG. 14 displays a flowchart of an example method 1400 for establishing,at least in part, access and control thereof to a femto AP, wherein theaccess can be exploited for macro-to-femto handover as described herein.It should be appreciated that while the subject method 1400 isillustrated for a femto AP, other indoor-based access points can beexploited. One or more network components (e.g., ID generator 710, aprovisioning server within server(s) 256) can implement the subjectexample method 1400. Additionally or alternatively, at least oneprocessor that confers, at least in part, functionality to the one ormore network components can enact the subject example method 1400. Atact 1410, a unique service area code (SAC) is supplied for each femtoaccess point in a femto mobile network. At act 1420, based at least inpart on the SAC, access privileges to each of the femto APs in the femtomobile network are configured for a mobile device. At act 1430, a MTF HOrequest to a target femto AP for a mobile device that is authorized toaccess the target femto AP is received, access is authorized based atleast in part on the SAC of the target femto AP and one or more uniqueidentifiers for the mobile device. At act 1440 the received MTF HOrequest is accepted. In an aspect, acceptance can be indicated throughsignaling 235 via an ACK signal; ACK signaling can be embodied, forexample, in one or more reserved bits in a packet header, alight-payload (e.g., of the order of 1 byte) data packet, apredetermined multi-bit word conveyed in a radio frame within a controlchannel, etc. At act 1450, preparation for MTF handover of the mobiledevice to the target femto AP is implemented. Preparation can includeone or more of the aspects described above.

To provide further context for various aspects of the subjectspecification, FIG. 15 and FIG. 16 illustrate, respectively, a blockdiagram of an example embodiment 1500 of a femtocell access point thatcan enable or exploit features or aspects of the subject innovation, andexample wireless network environment 1600 that includes femto and macronetwork platforms and that can enable or exploit aspects or features ofthe subject innovation described herein, and utilize femto APs thatexploit aspects of the subject innovation in accordance with variousaspects described herein.

In embodiment 1500, femto AP 1505 can receive and transmit signal(s)(e.g., attachment signaling) from and to wireless devices like femtoaccess points, access terminals, wireless ports and routers, or thelike, through a set of antennas 1520 ₁-1520 _(N) (N is a positiveinteger). It should be appreciated that antennas 1520 ₁-1520 _(N) embodyantenna(s) component 217, and are a part of communication platform 1515,which comprises electronic components and associated circuitry thatprovides for processing and manipulation of received signal(s) andsignal(s) to be transmitted. Such electronic components and circuitryembody at least in part signaling detection component 285; communicationplatform 1515 operates in substantially the same manner as communicationplatform 504 described hereinbefore. In an aspect, communicationplatform 1515 includes a receiver/transmitter 1516 that can convertsignal from analog to digital upon reception, and from digital to analogupon transmission. In addition, receiver/transmitter 1516 can divide asingle data stream into multiple, parallel data streams, or perform thereciprocal operation. Coupled to receiver/transmitter 1516 is amultiplexer/demultiplexer (mux/demux) component 1517 that facilitatesmanipulation of signal in time and frequency space. Electronic component1517 can multiplex information (data/traffic and control/signaling)according to various multiplexing schemes such as time divisionmultiplexing (TDM), frequency division multiplexing (FDM), orthogonalfrequency division multiplexing (OFDM), code division multiplexing(CDM), space division multiplexing (SDM). In addition, mux/demuxcomponent 1517 can scramble and spread information (e.g., codes)according to substantially any code known in the art; e.g.,Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, and soon. A modulator/demodulator (mod/demod) 1518 is also a part ofcommunication platform 1515, and can modulate information according tomultiple modulation techniques, such as frequency modulation, amplitudemodulation (e.g., M-ary quadrature amplitude modulation (QAM), with M apositive integer), phase-shift keying (PSK), and the like

Femto access point 1505 also includes processor(s) 1535 configured toconfer, and that confers, at least in part, functionality tosubstantially any component platform or interface, and related circuitryin femto AP 1505. In particular, processor(s) 1535 can enable, at leastpart, configuration of femto AP 1505, via control node(s) 1510. In anaspect, control node(s) 1510 can provision or configure an identifiercode such as SAC for femto AP 1505, wherein the identifier code can beretained in memory 1545. In another aspect, control node(s) 1510 cansupply system messages that can be broadcasted via communicationplatform 1515. In yet another aspect, control node(s) 1510 canautonomously adjust, as dictated at least in part by handover component254, transmitted power of pilot signal(s) delivered throughcommunication platform 1515 to mitigate signaling among a mobile devicethat hands over from macrocell coverage to femto coverage served throughfemto AP 1505.

Additionally, femto AP 1505 includes display interface 1512, which candisplay functions that control functionality of femto AP 1505, or revealoperation conditions thereof. In addition, display interface 1512 caninclude a screen to convey information to an end user. In an aspect,display interface 1512 can be a liquid crystal display (LCD), a plasmapanel, a monolithic thin-film based electrochromic display, and so on.Moreover, display interface can also include a component (e.g.,speaker(s)) that facilitates communication of aural indicia, which canalso be employed in connection with messages that convey operationalinstructions to an end user. Display interface 1512 also facilitatesdata entry (e.g., through a linked keypad or via touch gestures), whichcan facilitated femto AP 1505 to receive external commands (e.g.,restart operation).

Broadband network interface facilitates connection of femto AP 1505 tofemto network via backhaul link(s) 153 (not shown in FIG. 15), whichenables incoming and outgoing data flow. Broadband network interface1514 can be internal or external to femto AP 1505, and it can utilizedisplay interface 1512 for end-user interaction and status informationdelivery.

In an aspect, femto AP 1505 includes power supply 1525, which candeliver to components or functional elements within femto AP 1505, andcan regulate power output of wireless signal(s) emitted there from. Inan aspect, power supply 1525 can attach to a conventional power grid andinclude one or more transformers to achieve power level(s) that canoperate femto AP 1505 components, functional elements, and relatedcircuitry. Additionally, power supply 1525 can include a rechargeablepower component, e.g., a rechargeable battery, to ensure operation whenfemto AP 1505 is disconnected from the power grid.

Processor(s) 1535 also is functionally connected to communicationplatform 1515 and can facilitate operations on data (e.g., symbols,bits, or chips) for multiplexing/demultiplexing, such as effectingdirect and inverse fast Fourier transforms, selection of modulationrates, selection of data packet formats, inter-packet times, etc.Moreover, processor(s) 1535 is functionally connected, via data, system,or address bus 1511, to display interface 1512 and broadband networkinterface 1514 to confer, at least in part functionality to each of suchcomponents.

Memory 1545 also can store data structures, code instructions andprogram modules, or substantially any type of software or firmware;system or device information; code sequences hypotheses, and modulationand multiplexing hypotheses; spreading and pilot transmission; femto APfloor plan configuration; and so on. Furthermore, memory 1545 also canretain content(s) (e.g., multimedia files, subscriber-generated data);security credentials (e.g., passwords, encryption keys, digitalcertificates, biometric reference indicators like voice recordings, irispatterns, fingerprints); or the like. It is noted that memory 1545 canbe internal to femto AP 1505 and include removable and stationary memoryelements, or it can be an offline memory that is external to the femtoAP 1505 and is functionally coupled thereto through one or more links orinterfaces, e.g., USB, general purpose interface bus (GPIB), IEEE 1394,or the like. As an example, an offline memory can be a memory within aserver within a confined wireless environment served through femto AP1505.

Processor(s) 1535 is functionally coupled, e.g., via a memory bus, tothe memory 1545 in order to store and retrieve information necessary tooperate and/or confer functionality to the components, platform, andinterface that reside within femto access point 1505.

With respect to FIG. 16, wireless communication environment 1600includes two wireless network platforms: (i) A macro network platform1610 which serves, or facilitates communication with user equipment 1675(e.g., mobile 120 _(A)) via a macro radio access network (RAN) 1674. Itshould be appreciated that in cellular wireless technologies (e.g., 3GPPUMTS, HSPA, 3GPP LTE, 3GPP UMTS, 3GPP2 UMB), macro network platform 1610is embodied in a Core Network. (ii) A femto network platform 1680, whichcan provide communication with UE 1675 through a femto RAN 1690, whichis linked to the femto network platform 1680 via backhaul pipe(s) 1685(e.g., backhaul link(s) 153). It should be appreciated that macronetwork platform 1610 typically hands off UE 1675 to femto networkplatform 1610 once UE 1675 attaches, e.g., through macro-to-femtohandover as described herein, to femto RAN 1690, which includes a set ofdeployed femto APs (e.g., femto AP 130) that can operate in accordancewith aspects described herein.

It is noted that RAN includes base station(s), or access point(s), andits associated electronic circuitry and deployment site(s), in additionto a wireless radio link operated in accordance with the basestation(s). Accordingly, macro RAN 1674 can comprise various coveragecells like cells 105, while femto RAN 1690 can comprise multiplefemtocell access points such as femto AP 130. Deployment density infemto RAN 1690 is substantially higher than in macro RAN 1674.

Generally, both macro and femto network platforms 1610 and 1680 includecomponents, e.g., nodes, gateways, interfaces, servers, or platforms,that facilitate both packet-switched (PS) (e.g., internet protocol (IP),frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS)traffic (e.g., voice and data) and control generation for networkedwireless communication. In an aspect of the subject innovation, macronetwork platform 1610 includes CS gateway node(s) 1612 which caninterface CS traffic received from legacy networks like telephonynetwork(s) 1640 (e.g., public switched telephone network (PSTN), orpublic land mobile network (PLMN)) or a signaling system No. 7 (SS7)network 1660. Circuit switched gateway 1612 can authorize andauthenticate traffic (e.g., voice) arising from such networks.Additionally, CS gateway 1612 can access mobility, or roaming, datagenerated through SS7 network 1660; for instance, mobility data storedin a VLR, which can reside in memory 1630. Moreover, CS gateway node(s)1612 interfaces CS-based traffic and signaling and gateway node(s) 1618.As an example, in a 3GPP UMTS network, PS gateway node(s) 1618 can beembodied in gateway GPRS support node(s) (GGSN).

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 1618 can authorize and authenticatePS-based data sessions with served (e.g., through macro RAN) wirelessdevices. Data sessions can include traffic exchange with networksexternal to the macro network platform 1610, like wide area network(s)(WANs) 1650, enterprise networks (NW(s)) 1670 (e.g., enhanced 911), orservice NW(s) 1680 like IP multimedia subsystem; it should beappreciated that local area network(s) (LANs), which may be a part ofenterprise NW(s), can also be interfaced with macro network platform1610 through PS gateway node(s) 1618. Packet-switched gateway node(s)1618 generates packet data contexts when a data session is established.To that end, in an aspect, PS gateway node(s) 1618 can include a tunnelinterface (e.g., tunnel termination gateway (TTG) in 3GPP UMTSnetwork(s); not shown) which can facilitate packetized communicationwith disparate wireless network(s), such as Wi-Fi networks. It should befurther appreciated that the packetized communication can includemultiple flows that can be generated through server(s) 1614. It is to benoted that in 3GPP UMTS network(s), PS gateway node(s) 1618 (e.g., GGSN)and tunnel interface (e.g., TTG) comprise a packet data gateway (PDG).

Macro network platform 1610 also includes serving node(s) 1616 thatconvey the various packetized flows of information, or data streams,received through PS gateway node(s) 1618. As an example, in a 3GPP UMTSnetwork, serving node(s) can be embodied in serving GPRS support node(s)(SGSN).

As indicated above, server(s) 1614 in macro network platform 1610 canexecute numerous applications (e.g., location services, online gaming,wireless banking, wireless device management . . . ) that generatemultiple disparate packetized data streams or flows, and manage (e.g.,schedule, queue, format . . . ) such flows. Such application(s), forexample can include add-on features to standard services provided bymacro network platform 1610. Data streams can be conveyed to PS gatewaynode(s) 1618 for authorization/authentication and initiation of a datasession, and to serving node(s) 1616 for communication thereafter.Server(s) 1614 also can effect security (e.g., implement one or morefirewalls) of macro network platform 1610 to ensure network's operationand data integrity in addition to authorization and authenticationprocedures that CS gateway node(s) 1612 and PS gateway node(s) 1618 canenact. Moreover, server(s) 1614 can provision services from externalnetwork(s), e.g., WAN 1650, or Global Positioning System (GPS) or GNSSnetwork(s), which can be a part of enterprise NW(s) 1680. It is to benoted that server(s) 1614 can include at least one of a memory, one ormore processors configured to confer at least in part the functionalityof macro network platform 1610, and a bus which can include a memorybus, a system bus, an address bus or one or more reference link(s). Tothat end, the one or more processor can execute code instructions (notshown) stored in memory 1630, for example.

In example wireless environment 1600, memory 1630 stores informationrelated to operation of macro network platform 1610. Information caninclude business data associated with subscribers; market plans andstrategies, e.g., promotional campaigns, business partnerships;operational data for mobile devices served through macro networkplatform; service and privacy policies; end-user service logs for lawenforcement; and so forth. Memory 1630 can also store information fromat least one of telephony network(s) (NW(s)) 1640, WAN 1650, SS7 network1660, enterprise NW(s) 1670, or service NW(s) 1680.

Regarding femto network platform 1680, it includes a femto gatewaynode(s) 1684, which have substantially the same functionality as PSgateway node(s) 1618. Additionally, femto gateway node(s) 1684 can alsoinclude substantially all functionality of serving node(s) 1616.Disparate gateway node(s) 1684 can control or operate disparate sets ofdeployed femto APs, which can be a part of femto RAN 1690. In an aspectof the subject innovation, femto gateway node(s) 1684 can operate insubstantially the same manner as gateway node(s) 242. Control node(s)1620 can operate in substantially the same manner as control node(s)253, and can be distributed at least in part across a plurality of femtoaccess points that are part of RAN 1690.

Memory 1686 can retain additional information relevant to operation ofthe various components of femto network platform 1680. For exampleoperational information that can be stored in memory 1686 can comprise,but is not limited to, subscriber intelligence; contracted services;maintenance and service records; femtocell configuration (e.g., devicesserved through femto RAN 1690; authorized subscribers associated withone or more deployed femto APs); service policies and specifications;privacy policies; add-on features; so forth.

Server(s) 1682 have substantially the same functionality as described inconnection with server(s) 1614. In an aspect, server(s) 1682 can executemultiple application(s) that provide service (e.g., voice and data) towireless devices served through femto RAN 1690. Server(s) 1682 can alsoprovide security features to femto network platform. In addition,server(s) 1682 can manage (e.g., schedule, queue, format . . . )substantially all packetized flows (e.g., IP-based, frame relay-based,ATM-based) it generates in addition to data received from macro networkplatform 1610. Furthermore, server(s) 1682 can effect provisioning offemtocell service, and effect operations and maintenance. It is to benoted that server(s) 1682 can include at least one of a memory, one ormore processors configured to provide at least in part the functionalityof femto network platform 1680, and a bus which can include a memorybus, a system bus, an address bus or one or more reference link(s). Tothat end, the one or more processors can execute code instructions (notshown) stored in memory 1686, for example.

It is noted that femto network platform 1680 and macro network platform1610 can be functionally connected through one or more reference link(s)or reference interface(s). In addition, femto network platform 1680 canbe functionally coupled directly (not illustrated) to one or more ofexternal network(s) 1640-1680. Reference link(s) or interface(s) canfunctionally link at least one of gateway node(s) 1684 or server(s) 1682to the one or more external networks 1640-1680.

Various aspects or features described herein can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. In addition, various aspects disclosed inthe subject specification can also be implemented through programmodules stored in a memory and executed by a processor, or othercombination of hardware and software, or hardware and firmware. The term“article of manufacture” as used herein is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media. For example, computer readable media can include but are notlimited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips . . . ), optical disks (e.g., compact disc (CD), digitalversatile disc (DVD), blu-ray disc (BD) . . . ), smart cards, and flashmemory devices (e.g., card, stick, key drive . . . ).

It should be appreciated that while various aspects, features, oradvantages described herein have been illustrated through femto accesspoint(s) and associated femto coverage, such aspects and features alsocan be exploited for home access point(s) (HAPs) that provide wirelesscoverage through substantially any, or any, disparate telecommunicationtechnologies, such as for example Wi-Fi (wireless fidelity) or picocelltelecommunication. Additionally, aspects, features, or advantages of thesubject innovation can be exploited in substantially any wirelesstelecommunication, or radio, technology; for example, Wi-Fi, WorldwideInteroperability for Microwave Access (WiMAX), Enhanced General PacketRadio Service (Enhanced GPRS), 3GPP LTE, 3GPP2 UMB, 3GPP UMTS, HSPA,HSDPA, HSUPA, or LTE Advanced. Moreover, substantially all aspects ofthe subject innovation can include legacy telecommunicationtechnologies.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

What has been described above includes examples of systems and methodsthat provide advantages of the subject innovation. It is, of course, notpossible to describe every conceivable combination of components ormethodologies for purposes of describing the subject innovation, but oneof ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A method, comprising: assigning, by a systemcomprising a processor, service area code data indicative of a set ofservice area codes to respective femto access point devices; based onthe service area code data, configuring, by the system, access dataassociated with the respective femto access point devices, wherein theaccess data is indicative of an authorization for a mobile device toaccess the respective femto access point devices; receiving, by thesystem, macro-to-femto transfer data from the mobile device; in responseto verifying that the macro-to-femto transfer data comprises a requestto transfer a first coupling between the mobile device and a macroaccess point device to a second coupling between the mobile device and afemto access point device that is not part of the respective femtoaccess point devices, determining, by the system, whether the mobiledevice is authorized to access the femto access point device; and inresponse to determining, based on the access data and the service areacode data, that the mobile device is not authorized to access the femtoaccess point device, prohibiting, by the system, the mobile device frommeasuring a pilot signal representing channel quality data of the femtoaccess point device, and rejecting, by the system, the request totransfer the first coupling to the second coupling.
 2. The method ofclaim 1, wherein the femto access point device is a first femto accesspoint device, the request is a first request, and the method furthercomprises: in response to verifying that the macro-to-femto transferdata comprises a second request to transfer a first coupling to a thirdcoupling between the mobile device and a second femto access pointdevice of the respective femto access point devices, determining, by thesystem, that the mobile device is authorized to access the second femtoaccess point device; and in response to the determining that the mobiledevice is authorized to access the second femto access point device,accepting, by the system, the request to transfer the first coupling tothe third coupling.
 3. The method of claim 2, wherein the acceptingcomprises directing the macro-to-femto transfer data to the second femtoaccess point device to initiate the transfer the first coupling to thesecond coupling.
 4. The method of claim 1, wherein the receivingcomprises receiving identifier data indicative of the mobile device, andwherein the verifying comprises verifying based on the identifier data.5. The method of claim 4, wherein the receiving the identifier datacomprises receiving the identifier data based on shared network areaaccess data.
 6. The method of claim 4, wherein the receiving theidentifier data comprises receiving the identifier data based onsignaling data received from the mobile device during an initiation ofthe first coupling.
 7. The method of claim 1, further comprising:initiating, by the system, a transmission of the access data to themobile device.
 8. The method of claim 7, wherein the prohibitingcomprises: sending an instruction directed to the mobile device toinstruct the mobile device to prohibit scanning of the pilot signal. 9.The method of claim 8, wherein the set of the respective femto accesspoint devices is a first set of the respective femto access pointdevices and the method further comprises: instructing, by the system,the mobile device to initiate, based on the access data, scanning ofchannel quality data associated with a second set of the respectivefemto access point devices.
 10. The method of claim 1, furthercomprising: in response to determining that the macro-to-femto transferdata is associated with an emergency call, accepting, by the system, therequest to transfer the first coupling to the second coupling.
 11. Asystem, comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: associating service area codeswith respective femto access point devices; based on the service areacodes, determining access data associated with the respective femtoaccess point devices, wherein the access data specifies access rightsfor accessing the respective femto access point devices; receiving, froma mobile device, macro-to-femto transfer data indicative of a request totransfer a first coupling between the mobile device and a macro accesspoint device to a second coupling between the mobile device and a femtoaccess point device of the respective femto access point devices, and inresponse to determining, based on the access data and a service areacode of the service area codes corresponding to the femto access pointdevice, that the mobile device is not authorized to access the femtoaccess point device, prohibiting the mobile device from scanning a pilotsignal representing a signal condition of the femto access point deviceand prohibiting a transfer of the first coupling to the second coupling.12. The system of claim 11, wherein the receiving comprises receivingidentifier data indicative of the mobile device, wherein the identifierdata is utilized to facilitate the determining that the mobile device isnot authorized to access the femto access point device.
 13. The systemof claim 11, wherein the receiving the identifier data comprisesreceiving the identifier data based on shared network area access data.14. The system of claim 11, wherein the receiving the identifier datacomprises receiving the identifier data based on signaling data receivedfrom the mobile device during an initiation of the first coupling. 15.The system of claim 11, wherein the operations further comprise:directing the access data to the mobile device, wherein the access datais utilized to facilitate a determination of channel quality dataassociated with a set of the respective femto access point devices. 16.The system of claim 11, wherein the operations further comprise: inresponse to determining that the macro-to-femto transfer data isassociated with an emergency call, initiating the transfer of the firstcoupling to the second coupling.
 17. A computer-readable storage devicecomprising instructions that, in response to execution, cause a systemcomprising a processor to perform operations, comprising: assigningservice area code data indicative of a service area code to a femtoaccess point device; based on the service area code data, determiningaccess data associated with granting access of the femto access pointdevice to a mobile device; receiving, from the mobile device,macro-to-femto transfer data indicative of a request to transfer a firstcoupling between the mobile device and a macro access point device to asecond coupling between the mobile device and the femto access pointdevice; and in response to determining, based on the access data and theservice area code, that the mobile device is not authorized to accessthe femto access point device, prohibiting the mobile device fromscanning a pilot signal representing a signal condition of the femtoaccess point device and prohibiting a transfer of the first coupling tothe second coupling.
 18. The computer-readable storage device of claim17, wherein the operations further comprise: receiving comprisesreceiving identifier data representing the mobile device, wherein theidentifier data is utilized to facilitate the determining that themobile device is not authorized to access the femto access point device.19. The computer-readable storage device of claim 17, wherein theoperations further comprise: initiating a transmission of the accessdata to the mobile device, wherein the access data is utilized toinitiate a determination of channel quality data associated with a setof the respective femto access point devices.
 20. The computer-readablestorage device of claim 17, wherein the operations further comprise: inresponse to determining that the macro-to-femto transfer data isassociated with an emergency call, initiating the transfer of the firstcoupling to the second coupling.